Artifact-centric Business Process Model represents an operational model of business processes in which the changes and evolutions of business data, or business entities, are considered as the main driver of the processes. Different to current modeling approach which is so called Activity-centric or Process-Centric business process modeling, the Artifact-centric approach focuses on describing how business data is change/updated, by a particular action or task, throughout the process.
Contents |
In recent years, competitive business environment has forced companies to be operationally innovative in order to outperform their competitors. This challenge requires business process models not only to ensure work to be done as desired but also to enable operational innovations. In general, a process model describes activities conducted in order to achieve business goals, informational structure of a business, and organizational resources. Workflows, as a typical process modelling approach, often emphasize the sequencing of activities (i.e., control flows), but ignore the informational perspective or treat it only within the context of single activities. Without a complete view of the informational context, business actors often focus on what should be done instead of what can be done, hindering operational innovations.
Business process modeling is a foundation for design and management of business processes. Two key aspects of business process modeling are a formal framework that well integrates both control flow and data, and a set of tools to assist all aspects of a business process life cycle. A typical business process life cycle includes at least a design phase where the main concerns are around “correct” realization of business logic in a resource constrained environment, and an operational phase where a main objective is to optimize and improve the realization during the execution (operation). Traditional business process models emphasize heavily on a procedural and/or graph-based paradigm (a.k.a control flow). Thus, the methodologies to design workflows in those models are typically founded on a process-centric perspective. Recently, it has been argued that the consideration of data-centric perspective is especially useful for designing the detailed operation of business processes for enterprises in the modern era.
Intuitively, business artifacts (or simply artifacts) are data objects whose manipulations define in an important way the underlying processes in a business model. Not only the past and current practice of business process specification naturally embodies the artifacts, recent engineering and development efforts have already adopted the artifact approach in the process of design and analysis of business models. An important distinction between artifact centric models and traditional data flow (computational) models is that the notion of the life cycle of the data objects is prominent in the former, while not existing in the latter.
Recently, artiface-centric modeling has become an area of growing interest. Nigam and Caswell [1] introduced the concept of business artifacts and information-centric processing of artifact lifecycles. Kumaran et al. Further studies on artefact-centric business processes can be found in.[2][3][4] Bhattacharya [2] described a successful business engagement which applies business artifact techniques to industrialize discovery processes in pharmaceutical research. Liu et al.[4] formulated nine commonly used patterns in information-centric business operation models and developed a computational model based on Petri Nets. Bhattacharya, K., et al.[3] provides a formal model for artifact-centric business processes with complexity results concerning static analysis of the semantics of such processes. Kumaran et al.[5] presented the formalized information-centric approach to discovering business entities from activity-centric process models and transforming such models into artifact-centric business process models. An algorithm was provided to achieve this transformation automatically.
Other approaches related to artefact-centric modelling can be found in,.[6][7] Van der Aalst et al.[6] provides a case-handling approach where a process is driven by the presence of data objects instead of control flows. A case is similar to the business entity concept in many respects. Wang and Kumar [7] proposed the document-driven workflow systems which is designed based on data dependencies without the need for explicit control flows. Muller et al.[8] also introduced the framework for the data-driven modelling of large process structures, namely COREPRO. The approach reduces modelling efforts significantly and provides mechanisms for maintaining data-driven process structures.
Another related thread of work is the use of state machines to model object lifecycles. Industries often define data objects and standardize their lifecycles as state machines to facilitate interoperability between industry partners and enforce legal regulations.[9] Redding et al.[10] and Küster et al.[11] give techniques to generate business processes which are compliant with predefined object lifecycles. In addition, event-driven process modelling, for example, Event-driven Process Chains (EPC), also describes object lifecycles glued by events.
More recent and closely related work on artefact-centric process model can be found in.[12][13][14][15] Gerede and Su [12] developed a specification language ABSL to specify artifact behaviours in artifact-centric process models. The authors showed decidability results of our language for different cases and provided key insights on how artefact-centric view can affect the specification of desirable business properties. Gerede et al.[13] identified important classes of properties on artifact-centric operational models focusing on persistence, uniqueness and arrival properties. They proposed a formal model for artifact-centric operational models to enable a static analysis of these properties and showed that the formal model guarantees persistence and uniqueness.
Fritz, Hull, and Su [14] formulated the technical problem of goal-directed workflow construction in the context of declarative artifact-centric workflow, and develop results concerning the general setting, design time analysis, and the synthesis of workflow schemas from goal specifications. The work is among the important initial steps along the path towards eventual support for tools that enable substantial automation for workflow design, analysis, and modification. Deutsch et al.[15] introduced the artifact system model, which formalizes a business process modelling paradigm that has recently attracted the attention of both the industrial and research communities. The problem of automatic verification of artifact systems, with the goal of increasing confidence in the correctness of such business processes is also studied.
Sira and Chengfei [16] proposed a novel view framework for artifact-centric business processes. It consists of artifact-centric process model, process view model, a set of consistency rules, and the construction approach for building process views. The formal model of artifact-centric business processes and views, namely ACP, is defined and used to describe artifacts, services, business rules that control the processes, as well as views. They developed a bottom-up abstraction mechanism for process view construction to derive views from underlying process models according to view requirements. Consistency rules are also defined to preserve the consistency between constructed view and its underlying process. This work can be considered as one approach to the abstraction, i.e., generalization of artifact-centric business processes.
|
|||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||